MAINT: Explicitly re-export the types in numpy._typing
#21243
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Partial backport of #21216 (70176f6)
Closes #21214
This PR accomplishes two things:
It splitsnumpy.typing
into a public and private sub-package, allowing a greater degree of separation of the public interface from the list of private types and type-aliases. This one in particular has been on my wish list for some time due to the ever growing number of private members.numpy.typing
sub-package were already explicitly marked as re-exported, this was not the case for its' private members, resulting in BUG: Usage of implicit reexports breaks using mypy with--no-implicit-reexport
#21214. This issues has been rectified in 70176f6, which should be backported to 1.22.4 (I'll create a PR once this one is merged, as I anticipate a merge conflict or two).